CVE-2023-53337
nilfs2: do not write dirty data after degenerating to read-only
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buffer heads without the "uptodate" flag and causes the warning. Since any writes should not be done to a read-only file system in the first place, this fixes the warning in mark_buffer_dirty() by letting nilfs_segctor_do_construct() abort early if in read-only mode. This also changes the retry check of nilfs_segctor_write_out() to avoid unnecessary log write retries if it detects -EROFS that nilfs_segctor_do_construct() returned.
INFO
Published Date :
Sept. 17, 2025, 3:15 p.m.
Last Modified :
Sept. 17, 2025, 3:15 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Update the Linux kernel to the latest version.
- Ensure file systems are not marked read-only unnecessarily.
- Monitor for file system corruption warnings.
- Review kernel logs for related errors.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-53337.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-53337 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-53337
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-53337 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-53337 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 17, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: nilfs2: do not write dirty data after degenerating to read-only According to syzbot's report, mark_buffer_dirty() called from nilfs_segctor_do_construct() outputs a warning with some patterns after nilfs2 detects metadata corruption and degrades to read-only mode. After such read-only degeneration, page cache data may be cleared through nilfs_clear_dirty_page() which may also clear the uptodate flag for their buffer heads. However, even after the degeneration, log writes are still performed by unmount processing etc., which causes mark_buffer_dirty() to be called for buffer heads without the "uptodate" flag and causes the warning. Since any writes should not be done to a read-only file system in the first place, this fixes the warning in mark_buffer_dirty() by letting nilfs_segctor_do_construct() abort early if in read-only mode. This also changes the retry check of nilfs_segctor_write_out() to avoid unnecessary log write retries if it detects -EROFS that nilfs_segctor_do_construct() returned. Added Reference https://git.kernel.org/stable/c/13f73ef77baa4764dc1ca4fcbae9cade05b83866 Added Reference https://git.kernel.org/stable/c/28a65b49eb53e172d23567005465019658bfdb4d Added Reference https://git.kernel.org/stable/c/4005cec6847c06ee191583270b7cdd7e696543cc Added Reference https://git.kernel.org/stable/c/4569a292a84e340e97d178898ad1cfe1a3080a61 Added Reference https://git.kernel.org/stable/c/55f7810632f993cff622a0ddbc7c865892294b61 Added Reference https://git.kernel.org/stable/c/7c3e662048053802f6b0db3a78e97f4e1f7edc4f Added Reference https://git.kernel.org/stable/c/a73201c607d8e506358d60aafddda4246bdd9350 Added Reference https://git.kernel.org/stable/c/bd89073fc7a5d03b1d06b372addbe405e5a925f4 Added Reference https://git.kernel.org/stable/c/e9c5412c5972124776c1b873533eb39e287a4dfa